Skip to content

feat(@angular-devkit/build-angular): Add progress reporters for webpack builds#13405

Closed
GingerGeek wants to merge 1 commit into
angular:masterfrom
GingerGeek:build-progress-reporters
Closed

feat(@angular-devkit/build-angular): Add progress reporters for webpack builds#13405
GingerGeek wants to merge 1 commit into
angular:masterfrom
GingerGeek:build-progress-reporters

Conversation

@GingerGeek
Copy link
Copy Markdown

@GingerGeek GingerGeek commented Jan 10, 2019

  • Add progress reporters for webpack builds. Previously only the default webpack progress handler was used. The default handler did not display well in all CI environments as it attempted to use the same console line for all progress updates.
  • Add simple progress report, logging on new lines each time the build stage or build % changes.
  • Add verbose progress report, logging on new lines on every progress update with additional data provided by webpack.
  • Change default behaviour on non TTY consoles to use the simple progress report over the current behaviour of no progress reporting, this gives visibility over the status of build.

Previews

default-webpack

Delegate to default handler within ProgressPlugin in webpack (existing behaviour)
default-webpack

simple-color

Logging on new lines each time the build stage or build percentage changes (w/ colour)
simple-color

verbose-color

Logging on new lines on every progress update with additional data provided by webpack (w colour)
verbose-color

simple-plain

Logging on new lines each time the build stage or build percentage changes (w/o colour)
simple-plain

verbose-plain

Logging on new lines on every progress update with additional data provided by webpack (w/o colour)
verbose-plain

@googlebot
Copy link
Copy Markdown

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

@GingerGeek GingerGeek force-pushed the build-progress-reporters branch 2 times, most recently from bca7998 to 8341a89 Compare January 10, 2019 21:02
…ck builds

Add progress reporters for webpack builds. Previously only the default webpack
progress handler was used. The default handler did not display well in all CI
environments as it attempted to use the same console line for all progress updates.
Add simple progress report, logging on new lines each time the build stage or build
percentage changes.
Add verbose progress report, logging on new lines on every progress update with
additional data provided by webpack.
Change default behaviour on non TTY consoles to use the simple progress report over
the current behaviour of no progress reporting, this gives visibility over the status
of build.
@GingerGeek GingerGeek force-pushed the build-progress-reporters branch from 8341a89 to 6294fb9 Compare January 10, 2019 22:18
@GingerGeek
Copy link
Copy Markdown
Author

@googlebot CLA should be sorted!

@mgechev
Copy link
Copy Markdown
Member

mgechev commented Jan 11, 2019

@GingerGeek this is a large change and we should discuss further if we can merge it.

For such big changes, I'd recommend you to first open an issue so we can discuss if this is in the scope of the project.

@GingerGeek
Copy link
Copy Markdown
Author

@mgechev Apologies, I've created an issue to discuss this further: #13426

@filipesilva filipesilva self-assigned this Jan 24, 2019
@alexeagle alexeagle added the needs: discussion On the agenda for team meeting to determine next steps label Mar 27, 2019
@filipesilva filipesilva removed the needs: discussion On the agenda for team meeting to determine next steps label Mar 28, 2019
@mgechev
Copy link
Copy Markdown
Member

mgechev commented Aug 13, 2019

There are quite a few merge conflicts here and this PR has been open since January. Let's close it for now and keep the discussion in #13426. When we agree how to proceed forward, we can go with another PR.

@mgechev mgechev closed this Aug 13, 2019
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants